-
Notifications
You must be signed in to change notification settings - Fork 3.6k
[local_auth] Convert example app to Swift #11003
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
[local_auth] Convert example app to Swift #11003
Conversation
|
Changelog/version override: Native example app template details are not relevant to clients. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request converts the iOS example app for local_auth_darwin from Objective-C to Swift by regenerating the project from the latest Flutter stable template, updating project files and configurations. However, a critical vulnerability was introduced: the NSFaceIDUsageDescription key is missing from the Info.plist file. This absence will cause the app to crash when attempting biometric authentication with Face ID, making the example app non-functional on supported iOS hardware. Restoring this key is essential for the app to function correctly.
Replaces the Obj-C example app with Swift. Rather than attempt to modify the example in place, I started clean from the Swift template:
flutter create --platforms=ios .using currentstable(3.41.0).Pre-Review Checklist
[shared_preferences]pubspec.yamlwith an appropriate new version according to the pub versioning philosophy, or I have commented below to indicate which version change exemption this PR falls under1.CHANGELOG.mdto add a description of the change, following repository CHANGELOG style, or I have commented below to indicate which CHANGELOG exemption this PR falls under1.///).Footnotes
Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩2 ↩3